Application-based backup-restore of electronic information

ABSTRACT

Systems and methods for storing and restoring backup data. One method includes receiving, while a current view of an application is displayed in a user interface, a first user input requesting a history view associated with the current view of the application. The history view is displayed in response to the first user input, the history view including at least a first visual representation of an earlier version of the current view of the application, the earlier version including a first element. A second user input is received while the history view is displayed. The second user input requesting that the current view of the application be modified according to the earlier version, at least with regard to the first element. The current view of the application is modified in response to the second user input according to the earlier version, at least with regard to the first element.

RELATED APPLICATIONS

This application is generally related to the following jointly owned andco-pending patent applications, each incorporated herein by reference inits entirety:

U.S. patent application Ser. No. ______, for “Managing Backup ofContent,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “User Interface for BackupManagement,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Navigation of ElectronicBackups,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Architecture for Back Upand/or Recovery of Electronic Data,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Searching a BackupArchive,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Conflict Resolution inRecovery of Electronic Data,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “System for Multi-DeviceElectronic Backup,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “System for ElectronicBackup,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Restoring ElectronicInformation,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Links to a Common Item ina Data Structure,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Event NotificationManagement,” filed Aug. 4, 2006;

U.S. patent application Ser. No. ______, for “Consistent Back Up ofElectronic Information,” filed Aug. 4, 2006.

TECHNICAL FIELD

The disclosed implementations relate generally to storing and restoringdata.

BACKGROUND

A hallmark of modern graphical user interfaces is that they allow alarge number of graphical objects or items to be displayed on a displayscreen at the same time. Leading personal computer operating systems,such as Apple Mac OS®, provide user interfaces in which a number ofwindows can be displayed, overlapped, resized, moved, configured, andreformatted according to the needs of the user or application. Taskbars,menus, virtual buttons and other user interface elements providemechanisms for accessing and activating windows even when they arehidden behind other windows.

With the sophisticated tools available, users are encouraged not only tocreate and save a multitude of items in their computers, but to reviseor otherwise improve on them over time. For example, a user can workwith a certain file and thereafter save its current version on a storagedevice. The next day, however, the user may have had second thoughtsabout the revisions, or may have come up with new ideas, and thereforeopens the file again.

The revision process is usually straightforward if the user wants to addmore material to the file or make changes to what is there. But it istypically more difficult for a user who has changed his/her mind aboutchanges that were previously made and wants the file back as it was oncebefore. Application programs for word processing typically let the user“undo” previous edits of a text, at least up to a predefined number ofpast revisions. The undo feature also usually is configured so that thepreviously made revisions must be undone in reverse chronological order;that is, the user must first undo the most recently made edit, then thesecond-most recent one, and so on. If the user saves and closes thedocument and thereafter opens it again, it may not be possible toautomatically undo any previous edits.

SUMMARY

Systems and methods are provided for storing and restoring backup data.The backup data can relate to previous state of particular applications.The previous states of the applications can be presented in a backupinterface. In one implementation, a user can enter the backup interfacefrom the application window (e.g., iTunes). Views presented in thebackup interface can represent past states of the application (e.g.,state of the iTunes library).

In general, in one aspect, a method is provided. The method includesreceiving, while a current view of an application is displayed in a userinterface, a first user input requesting that a history view associatedwith the current view of the application be displayed. The history viewis displayed in response to the first user input, the history viewincluding at least a first visual representation of an earlier versionof the current view of the application, the earlier version including afirst element. A second user input is received while the history view isdisplayed. The second user input requesting that the current view of theapplication be modified according to the earlier version, at least withregard to the first element. The current view of the application ismodified in response to the second user input according to the earlierversion, at least with regard to the first element.

Implementations of the method can include one or more of the followingfeatures. The first user input requesting the history view can beinitiated in the current view of the application. The second user inputcan request that the modification be limited to the first element, andwherein the modification modifies the current view of the application toinclude the first element and does not otherwise modify the current viewof the application.

The first element can be a particular set of application data that isnot stored as typical file data. The set of application data can includemail messages, address book entries, or audio data. The first visualrepresentation can be included in a timeline presented in the historyview, the timeline including several visual representations of earlierversions of the current view of the application. The earlier versions ofthe current view of the application can be obtained at times defined bya schedule or by a rule. The earlier versions of the current view of theapplication can be obtained at times when at least one predefined eventoccurred.

The history view can further include an input control for modifying thetimeline to include only at least one of the visual representationswhose corresponding earlier version differs from the current view of theapplication. The history view can further include a rollover functionproviding that the timeline is displayed when a user-controlled cursoris located over the timeline, and that the timeline is not displayedwhen the user-controlled cursor is not located over the timeline. Theapplication can be an audio application and the first element can be aplaylist. The application can be an e-mail application and the firstelement can be an inbox. The application can be an e-mail applicationand the first element can be a calendar. The application can be anaddress book application and the first element can be a directory ofcontacts. The application can be a messaging application and the firstelement can be a buddy list.

In general, in one aspect, a computer program product is provided. Thecomputer program product includes instructions to generate on a displaydevice a user interface. The user interface includes a view display areafor presenting a current view of an application. The user interface alsoincludes a history view display area for presenting a history viewassociated with the current view of the application, the history viewincluding at least a first visual representation of an earlier versionof the current view of the application and an input control forinitiating a restoration of the current view of the applicationaccording to at least a portion of the earlier version.

Implementations can include one or more of the following features. Theearlier version can include at least a first element that a user canselect, and wherein initiation of the input control after the selectioninitiates the restoration of the current view of the applicationaccording to only the first element of the earlier version. The firstvisual representation can be included in a timeline presented in thehistory view, the timeline including several visual representations ofearlier versions of the current view of the application. The historyview can further include another input control for modifying thetimeline to include only at least one of the visual representationswhose corresponding earlier version differs from the current view of theapplication.

In general, in one aspect, a method is provided. The method includesdefining one or more criteria for capturing a state of a view of a userinterface of an application. The state of the view is captured inaccordance with the criteria. A prompt is received to suspendpresentation of a current view and present a captured view. The capturedview is reinstated into the current view of the user interface. Definingthe one or more criteria can include receiving a user input in the userinterface of the application setting one or more parameters associatedwith the one or more criteria.

In general, in one aspect, a method is provided. The method includesreceiving, while a current view of a system settings interface isdisplayed in a user interface, a first user input requesting that ahistory view associated with the current view of the system settingsinterface be displayed. The history view is displayed in response to thefirst user input, the history view including at least a first visualrepresentation of an earlier version of the current view of the systemsetting interface, the earlier version including one or morepreferences. A second user input is received while the history view isdisplayed. The second user input requests that the current view of thesystem settings interface be modified according to the earlier version,at least with regard to a first preference of the one or morepreferences. The current view of the system settings interface aremodified in response to the second user input according to the earlierversion, at least with regard to the first preference.

Implementations can include one or more of the following features. Thesystem settings interface can be an input device settings interface andthe one or more preferences are keyboard and mouse settings. The systemsettings interface can be a user interface settings interface and theone or more preferences are user interface preferences.

The details of the various aspects of the subject matter described inthis specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of theinvention will become apparent from the description, the drawings, andthe claims.

BRIEF DESCRIPTION FO THE DRAWINGS

FIG. 1 is a block diagram of an example of an architecture for modifyinga user interface view in a display environment.

FIG. 2 is a block diagram of an example of an architecture for backingup and restoring application files.

FIG. 3 is a screen shot depicting an example of a desktop user interfacewith multiple open applications.

FIG. 4 is a screen shot depicting an example of an initial state for atime machine user interface after the time machine engine has beenactivated.

FIG. 5 is a screen shot depicting the time machine interface of FIG. 4where a snapshot has been selected.

FIG. 6 is a screen shot depicting the time machine interface of FIG. 5wherein a portion of a snapshot has been selected for restoration.

FIG. 7 is a screen shot showing the desktop user interface after somecontents from an earlier version have been restored using the timemachine engine.

FIG. 8 is a screen shot depicting an example of a desktop user interfacewith multiple open applications.

FIG. 9 is a screen shot depicting an example of a state for a timemachine user interface after the time machine engine has been activated.

FIG. 10 is a screen shot depicting an example showing changed items in atime machine user interface.

FIG. 11 is a screen shot depicting the time machine interface after thetime machine engine has been activated.

FIG. 12 is a screen shot depicting the time machine interface of FIG. 11where a snapshot has been selected in the timeline.

FIG. 13 is a screen shot depicting the time machine interface wherecontents of a snapshot have been selected.

FIG. 14 is a screen shot showing another example of the desktop userinterface after some contents from an earlier version have been restoredusing the time machine engine.

FIG. 15 is a screen shot showing the time machine interface used with a“Keyboard & Mouse” settings pane.

FIG. 16 is a screen shot showing the time machine interface for anaddress book application.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an architecture 100 for capturing at leastone earlier version of a user interface view and allowing a user toinitiate a restoration based on it. As used herein, a view refers to anitem, element, or other content, capable of being stored and/orretrieved in an interface, that can be subjected to a backup operationby a backup component 117. For example, a user interface view cancontain any number of icons, files, folders, application stateinformation and/or machine state information, preferences, etc. Thearchitecture 100 includes a personal computer 102 communicativelycoupled to a remote server 107 via a network interface 116 and a network108 (e.g., local area network, wireless network, Internet, intranet,etc.). The computer 102 generally includes a processor 103, memory 105,one or more input devices 114 (e.g., keyboard, mouse, etc.) and one ormore output devices 115 (e.g., a display device). A user interacts withthe architecture 100 via the input and output devices 114, 115.Architecture 100 as disclosed includes various hardware elements.Architecture 100 can include hardware, software, and combinations of thetwo.

The computer 102 also includes a local storage device 106 and a graphicsmodule 113 (e.g., graphics card) for storing information and generatinggraphical objects, respectively. The local storage device 106 can be acomputer-readable medium. The term “computer-readable medium” refers toany medium that includes data and/or participates in providinginstructions to a processor for execution, including without limitation,non-volatile media (e.g., optical or magnetic disks), volatile media(e.g., memory) and transmission media. Transmission media includes,without limitation, coaxial cables, copper wire, fiber optics, andcomputer buses. Transmission media can also take the form of acoustic,light or radio frequency waves.

While modifications of a user interface view are described herein withrespect to a personal computer 102, it should be apparent that thedisclosed implementations can be incorporated in, or integrated with,any electronic device that has a user interface, including withoutlimitation, portable and desktop computers, servers, electronics, mediaplayers, game devices, mobile phones, email devices, personal digitalassistants (PDAs), embedded devices, televisions, other consumerelectronic devices, etc.

Systems and methods are provided for modifying an interface view (e.g.,a user interface view). The systems and methods can be stand alone, orotherwise integrated into a more comprehensive application. In thematerials presented below, an integrated system and method for modifyinga user interface view is disclosed. However, one of ordinary skill inthe art will recognize that the engines, methods, processes and the likethat are described can themselves be an individual process orapplication, part of an operating system, a plug-in, an application orthe like.

In one implementation, the system and methods can be implemented as oneor more plug-ins that are installed and run on the personal computer102. The plug-ins are configured to interact with an operating system(e.g., MAC OS® X, WINDOWS XP, LINUX, etc.) and to perform the variousfunctions, as described with respect to the Figures. A system and methodfor modifying a user interface view can also be implemented as one ormore software applications running on the computer 102. Such a systemand method can be characterized as a framework or model that can beimplemented on various platforms and/or networks (e.g., client/servernetworks, wireless networks, stand-alone computers, portable electronicdevices, mobile phones, etc.), and/or embedded or bundled with one ormore software applications (e.g., email, media player, browser, etc.).

The computer 102 includes the backup component 117 that allows for thestorage of versions of the computer's files or other items, for examplewithin the local storage 106 or in an external storage repository. Inone implementation, the backup component 117 also allows a user toselect any of the stored versions and use it to initiate a restorationof that version in the computer.

FIG. 2 is a block diagram of an exemplary architecture (e.g., softwarearchitecture) 200 for enabling the back up and restoration ofapplication files, such as those associated with a set of applicationprograms 228.

Each application program 228 can include an application programminginterface (API) 229. The architecture 200 can utilize API 229 techniquesto enhance application programs with further functionality. For example,the API 229 can link several applications together for providing asingle service on all linked applications. Particularly, the timemachine architecture can utilize API techniques to enhance applicationprograms with the time machine functionality. The API tools can linkseveral applications to the time machine engine by using an API forproviding a similar menu or icon for each application. For example, theAPI can be used by the time machine when generating a backup version ofa current state of the application. As another example, the API can beused when the application is restored, through the time machine, to astate that corresponds to a backup version. Although API 229 is shown inFIG. 2 as part of application programs 228, the API can be separate fromthe application programs 228. For example, the API 229 can be separatelylocated and made available by the system for use by one or more of theapplication programs 228.

In one implementation, the backup component 117 provides back up andrestoration capability for the system. Many different items or elementscan be the subject of a backup in the system. For example, folders,files, items, information portions, directories, images, systemparameters, playlists, address books, e-mails, e-mail folders, a stateof an application or state of the system, preferences (e.g., user orsystem preferences), and the like all can be candidates for archiving.Other types are also possible. In this example, the backup component 117includes a local storage device 204 and an external storage device 232.Versions can be stored on either of them. Any number of local and/orexternal storage devices can be used by the backup component 117 forstoring versions. In one implementation, no local storage is provided.

The backup component 117 can interact with one or more of theapplications using the corresponding API. In one implementation, thiscan provide backing up of that application's files, state or otheritems, and can provide for user restoration of a selected backed upversion, to name two examples. In one implementation, the backupcomponent 117 runs as a background task on an operating system 230 thatis not visible to the user. The backup component 117 can be capable ofrunning across multiple user accounts.

The backup component 117 includes an activity monitoring engine 212. Inone implementation, the activity monitoring engine 212 monitors forchanges within applications (e.g., application files or state) that aretargeted for backup operations. A change can also include the additionof new files or other data structures, or deletion of existing ones.

In one implementation, the activity monitoring engine 212 is capable ofdiscerning between a substantive change (e.g. the text within a documenthas been modified) and a non-substantive change (e.g. the play countwithin an iTunes playlist has been updated, or several changes canceleach other out) through its interaction with the application programs228. The activity monitoring engine 212 can, for example, create a listof modified elements to be used when a backup event is eventuallytriggered. In one implementation, the activity monitoring engine 212 canmonitor the system for periods of inactivity. The activity monitoringengine 212 can then trigger a backup event during a period of time inwhich the backup operation will not cause a system slowdown for anactive user.

A preference management engine 214 specifies some operating parametersof the backup component 117. In one implementation, preferencemanagement engine 214 contains user-specified and/or system defaultapplication parameters for the backup component 117. These can includesettings for the details of capturing and storing the views. Forexample, the preference management engine 214 can determine thefrequency of a backup capture, the storage location for the backupversions, the types of elements (e.g., files or other items) that areeligible for backup capture, and the events which trigger a backupcapture (periodic or event-driven, etc.).

In one implementation, the preference management engine 214 can detectthat a new storage device is being added to the system and prompt theuser whether it should be included as a backup repository. Files andother items can be scheduled for a backup operation due to location(e.g. everything on the C: drive and within D:/photos), a correlationwith specific applications (e.g. all pictures, music, e-mail in aninbox, an address book, and system settings), or a combination ofstrategies. Different types of items can be scheduled to be stored ondifferent devices or on different segments of a storage device during abackup operation. In one implementation, the backup component 117 storesthe versions in a format corresponding to a file system structure.

A backup management engine 216 coordinates the collection, storage, andretrieval of views performed by the backup component 117. For example,the backup management engine 216 can trigger the activity monitoringengine 212 to watch for activities that satisfy a requirement specifiedin the preference management engine 214.

A change identifying engine 218 locates specific elements (e.g.,monitored files or other items within) to determine if they havechanged. The change identifying engine 218 can be capable of discerninga substantive change from a non-substantive change, similar to theexample described above for the activity monitoring engine 212. In oneimplementation, the change identifying engine 218 traverses a target setof elements (e.g., files or other items), comparing a previous versionto the current version to determine whether or not a modification hasoccurred.

A backup capture engine 220 locates views (e.g., elements, files orother items) that are to be backed up. The backup capture engine 220 caninvoke the activity monitoring engine 212 and/or the change identifyingengine 218, for example, to generate a capture list. The backup captureengine 220 can then store copies of these elements in one or moretargeted storage repositories. The backup capture engine 220 can trackmultiple version copies of each item included in the backup repository.

The backup component 117 includes a backup restoration engine 222 torestore previous versions of views (e.g., files or other items). In oneimplementation, the backup restoration engine 222 provides a userinterface (e.g., a graphical user interface) where a user can select theitem(s) to be restored.

FIG. 3 is a screen shot depicting an example of a user interface 300(e.g., a desktop user interface) with multiple open applications. Theuser interface 300 can be a user interface as may be provided by anoperating system. The user interface 300 has a background, a menu bar302, an application launch bar 304, and may include windows, icons, andother elements. Other configurations are possible. The user interface300 can have multiple applications running, any or all of which can bepresented in a separate window. While working with the applications, orat some other time, a user can initiate a time machine session in thesystem.

As shown in FIG. 3 a user has launched an iTunes™ application window(available from Apple Computer in Cupertino, Calif.) which is currentlypresented in the foreground, and a chat application 308 and a mailapplication 310 that are presented in the background. In particular, theiTunes™ application is here displaying contents of the user's library,which lists the user's songs. The iTunes™ application can be used foraccessing, playing and organizing media, such as digital music, picturesand video files.

The time machine application can be activated to back up or restoremedia content within the iTunes™ application or another application. Inone implementation, the user can activate a time machine session fromthe user interface using a user-selectable time machine icon 312 in theapplication launch bar 304. As another example, the time machine sessioncan be activated from the menu bar 102. The menu bar 302 can include atime machine options menu in addition to the activation selection. Thetime machine options menu can include selections allowing a user tospecify data to include in a particular backup. For example, in iTunes™,the user can identify which content to back up (e.g., playlists, but notplay counts, purchased songs, but not others, etc.). In addition, theuser can recover songs that were previously included, but are nowmissing from the iTunes™ library. For example, the user can have made atleast one backup of the missing songs at an earlier date, and can enterthe time machine to search for the missing songs or files in a backupsnapshot of the iTunes™ application allowing for the restoration of aview corresponding to that prior time. As used herein, a snapshot refersto a backup element stored in a historical archive that includes abackup of selected items or content as specified by the backup component117. In other implementations, the user can choose to enter the timemachine directly from an operating system menu. In some implementations,the time machine architecture can include several icons or menusavailable in other locations within the user interface 300 or runningapplications, thereby providing several options for activating orlaunching the time machine engine.

FIG. 4 is a screen shot depicting an example of an initial state for atime machine user interface 400 after the time machine engine has beenactivated. The time machine interface 400 here includes a presentationwindow 401, a timeline 402, and function buttons. As shown, thepresentation window 401 is displaying the current iTunes™ applicationfrom FIG. 3 because a “current” snapshot 404 has been selected(highlighted) in the timeline. The current snapshot can be a defaultselection. The presentation window 401 can show the contentscorresponding to the currently selected snapshot, or a portion thereof.In this particular example, there is presented a date beneath eachsnapshot indicating when the snapshot was taken. In someimplementations, the user can select items or content within thesnapshots. For example, the user can select the snapshot 404, and nextselect one or more songs to back up using the time machine interface400. In addition, the same selection functionality can be used inprevious snapshots, such as snapshot 414, to restore missing data to thestate associated with the current snapshot 404.

The timeline 402 can include a number of snapshots representing earlierversions or states of the iTunes™ library that have been backed up. Eachsnapshot provides a screenshot representation of the earlier version ofthe iTunes™ library at a particular point in time. In someimplementations, the timeline 402 includes a visual representation ofbackup elements, such as a miniature version of the earlier state. Thetime line can appear across the top portion of the time machineinterface 402 (as shown). Alternatively, the timeline may not appear inthe top portion of the time machine interface 400 until a user movestheir cursor to (or otherwise activates) the timeline (e.g., byactivating the top portion of the interface).

The time machine user interface 400 can also include function controls.For example, the interface 400 can include arrow buttons 406 a and 406 bto navigate the snapshots forward or backward. Arrow buttons 408 a and408 b can allow the user to navigate to additional snapshots not shownin the current timeline window, thus there can be a large number ofsnapshots from which to select.

The interface can include a restore button 410 that, when selected,restores the view to the selected state represented by the selectedsnapshot. In some implementations, this terminates the session of thetime machine. A user can select one element in a snapshot and thenselect the restore button 410 to modify the current version of theelement selected (e.g., restore the state of the view). For example, iniTunes™, the user can select a few songs to restore, and this cantrigger the restore button to display a more precise message, such as“restore selection only.”

In one implementation, a changed items only checkbox control 412 filtersthe snapshots to show only those that differ from the current state. Inone implementation, the checkbox control 412 does not refer to theincremental changes between snapshots in the timeline 402, but ratherwhen invoked acts to omit those snapshots whose states are identical tothe current state of the iTunes™ library from presentation in thetimeline. For example, if the most recent snapshot 404 is identical tothe snapshot 414 that occurs earlier in time, selecting the changeditems only checkbox control 412, in one implementation, causes the timemachine to cease displaying one of these versions, e.g., by removing thesnapshot 414 from the timeline. This can help the user to view onlysnapshots that contain changes to the current version.

An information button 416 provides information regarding the selectedsnapshot. In one implementation, selecting the information button 416opens a panel display. The panel display can provide informationincluding the date and time the snapshot was made, the location ofactual contents in a snapshot, the size of the snapshot, and a commentsection, to name a few examples. A close button 418 can be selected toexit the time machine and return the user to the user interface 300. Insome implementations, the time machine engine can automatically closeupon a particular snapshot being restored. In some implementations, theuser can minimize the time machine for purposes of navigating to otherapplications, such as an email application or a web browser.

FIG. 5 is a screen shot depicting the time machine interface 400 where asnapshot 502 has been selected in the timeline. The iTunes™ applicationinterface corresponding to the selected snapshot 502 (labeled Jan. 30,2006) is displayed in the presentation window 401. This earlier versionof the iTunes™ application shows a file tree where the user has selecteda source library 506, which can contain several songs and albums. Thesongs and albums can be sorted and arranged by name, length, artist, oralbum title, to name a few examples. In some implementations, othersorting fields can be used, such as sorting by genre. In addition, theuser can use the information in the source library 506 to createseparate song lists known as playlists. Playlists can combine severalartists and albums in one list and can be presented in a user-selectedorder. Playlists can also be burned to compact discs, transferred to aniPod™ device (available from Apple Computer in Cupertino, Calif.), orplayed on the computer device 102.

In this example, the source library displayed in the selected snapshot502 includes songs that are not found in the current version of thelibrary. In particular, those include twelve songs by the artist“Gorillaz.” For example, the user can delete these twelve songs from thesource library 506 after the earlier version was backed up. The user maywish to restore these twelve missing songs and can do so by using thetime machine user interface 400. FIG. 6 illustrates one implementationof the restoration of partial content from a snapshot.

FIG. 6 is a screen shot depicting the time machine interface of FIG. 5wherein a portion of a snapshot has been selected for restoration. Forexample, the user can select the twelve missing songs 602 within thesnapshot 502 displayed in the presentation window. Thus, as with theearlier described implementation, the user can select items or partialcontent within the snapshots. Upon selecting the missing songs 602 insome implementations, the restore button can change, as shown, from“Restore All” 410 to “Restore 12 Songs” 604. If the user selects the“Restore 12 Songs” button 604, the selects songs will be restored to thelibrary of the current iTunes™ application. Upon selecting the restorebutton 604, the time machine engine can exit and return the user to theuser interface 300. In some implementations, the user can choose toremain in the time machine to perform further restorations.

FIG. 7 is a screen shot showing the user interface 300 after somecontents from an earlier version have been restored using the timemachine engine. As shown, the iTunes™ library 506 now includes therestored twelve songs. In this example, actual data content representedby one snapshot was collected and restored in the iTunes™ application.Alternatively, the time machine application can restore only theorganization of the data. For example, in iTunes™, the user can have anumber of different playlists, such as the “Party Shuffle” playlist 702.Each playlist can contain a different set of songs. In general, songswhich appear in more than one playlist do not correspond to multiplecopies of the song because the playlist is considered a particularorganization of songs in the source library 506. Therefore, if the userrestores a playlist using the time machine application, only theplaylist organization can require restoration. Thus, the underlyingsongs do not require restoration in such an example, unless they aremissing from the source library 506. These and other types of non-fileform data (e.g., metadata or other application data) can be restoredusing the time machine engine.

FIG. 8 is a screen shot depicting an example of a desktop user interfacewith multiple open applications. A user has launched an iPhoto™application window 802, (available from Apple Computer in Cupertino,Calif.) which is currently presented in the foreground, and a chatapplication 804 and a mail application 806 that are presented in thebackground. In particular, the iPhoto™ application is here displayingcontents of the user's library, which lists the user's photo albumscontaining photographs. The iPhoto™ application can be used foraccessing, storing, and organizing media, such as images, scannedphotographs, and video content. While working with the applications, orat some other time, a user can initiate a time machine session in thesystem.

As shown in FIG. 8, there is a source pane 808 in the application window802 for navigating the content. For example, the user can select aparticular photo album to view the contents in the photo album (e.g.photographs, images, and video content). In this example, the user hasselected a “Library” item 810, and the iPhoto™ application has presentedto the user all of the images in the library 810. In someimplementations, the user can select one or more albums to display thecontents of each such album in the iPhoto™ application. For example, theuser can select a “Last 12 Months” photo album 812, and this can displayall images collected in the selected album in the application window102. In some implementations, the contents can be displayed as thumbnailimages, such as thumbnail image 814. In other implementations, thecontents can be displayed in list form using the file name as thedisplayed image. The contents in each photo album can be different setsof images, for example, organized by event, theme, time, category, andthe like. In some implementations, a photograph count 816 can bepresented to the user showing how many images are in the currentapplication window 802. In general, the user can create, delete, ortransfer images in the photo albums and the photograph count 816 canadjust accordingly when a photograph is added or deleted from theapplication window 802, or when the user switches between photo albums.As shown, the photograph count 816 displays “1,973 photos,” indicatingthat there are 1,973 photographs in the current user library 810.

In addition to creating, deleting and transferring images in the photoalbum, the user can also modify the images by selecting variousphotograph options shown in a control panel 818. The control panel 818can include options allowing the user to rotate, edit, email, orgenerally move the images into other configurations. For example, thecontrol panel 818 can present options to the user to select images fromseveral photo albums to create a book or calendar entry using theselected images. As another example, the panel 818 provides that theuser can search for images using the application.

FIG. 9 is a screen shot depicting an example of a state for a timemachine user interface 902 after the time machine engine has beenactivated. The presentation window 904 is displaying a “Jan. 9-Jan. 23,2005” snapshot 906 of the iPhoto™ application, for example because theuser has selected this particular snapshot from the timeline 908.Generally, the time machine in some implementations provides that anexact replica of the selected snapshot can be restored. However, in someimplementations, the user can select a “Show changed items only”checkbox 910 to modify the content to be presented in the interface 902.For example, when the checkbox 910 has been selected, the timeline canadjust to display only items with reference to the “Current” snapshot912. An example of selecting the “Show changed items only” checkbox 910is described with reference to FIG. 10.

FIG. 10 is a screen shot depicting an example showing changed items in atime machine user interface. In particular, the user has checked the“Show changed items only” checkbox 910 for purposes of restoring onlythe changed items in the “Current” snapshot 912. When the checkbox 910is selected, all images that are present in the “Current” snapshot 912are deleted from the prior snapshots. For example, the “Jan. 9-Jan. 23,2005” snapshot 906 shows the four photographs that are not present inthe “Current” snapshot 912. Thus, when the checkbox 910 is selected, thecontent of each snapshot is presented relative to the content of thecurrent snapshot. In another implementation, the checkbox 910 can filterout snapshots in the timeline that are identical to the currentsnapshot, and leave the remaining snapshots intact.

FIG. 11 is a screen shot depicting the time machine interface after thetime machine engine has been activated. The iPhoto™ application fromFIG. 8 corresponding to a current snapshot 1102 is being presented inthe presentation window 802. A timeline 1104 contains a set of iPhoto™snapshots, each of which includes a date indicating when the snapshotwas taken. In some implementations, a date range can be displayedindicating that the content in the snapshot is the same throughout thetime period, as shown, for example, in snapshot 1106. Navigation 1108,restore 1110 and information 1112 function buttons can operatesubstantially as described earlier with reference to FIG. 3. Thesnapshots shown in the timeline 1104 can be images representing theiPhoto™ application showing the state of a source library 1114 for eachsnapshot. The user can navigate between snapshots with the image shownin the presentation window 802 corresponding to the selected snapshot.

FIG. 12 is a screen shot depicting the time machine interface of FIG. 11where a snapshot 1202 has been selected in the timeline. The iPhoto™application interface corresponding to the selected snapshot 1202 (Jan.9-Jan. 23, 2005) is displayed in the presentation window 802. Here, theuser can search for a photo album that is not present in the currentsnapshot 102, such as the “Euro 2004” album. The selected snapshot 1202includes the Euro 2004 album. Accordingly, the user can navigate to thissnapshot to access the content thereof (the Euro 2004 folder) that isnot present in the current version. As shown, the number of photographs816 in the snapshot 1202 is 1,912, whereas the current snapshot 1102contains 1,973 pictures.

FIG. 13 is a screen shot depicting the time machine interface where asnapshot 1202 has been selected in the timeline. As shown, the albumdepicted in the snapshot 1202 is the “Euro 2004” album 1204. Upon theuser selecting the snapshot 1202, the user can then select the “Euro2004” album 1204. This can, in turn, trigger the interface to presentthe backed up data for the “Euro 2004” album 1204. The user can select arestore button 1312 to restore the content of the “Euro 2004” albumalong with all other contents in the corresponding earlier version. Asanother example, the user can choose to restore only a portion of thesnapshot 1202 by selecting at least one image in the presentation window802. For example, to restore only image 1314, the user can select theimage and then select the restore button 1312. Selecting the restorebutton causes the album 1204, or a selected portion thereof, to berestored in the current view of the iPhoto™ application and isthereafter accessible to the user. For example, the album 1204 can berestored to the source library in the iPhoto™ application allowing theuser to modify the contents in the album 1204. In some implementations,the restore button caption can change to “Restore 1 image” when a userselects one image.

FIG. 14 is a screen shot showing another example of the desktop userinterface after some contents from an earlier version have been restoredusing the time machine application. Particularly, the user here selectedthe Euro 2004 folder for restoration. As shown, the iPhoto™ library 1114now includes the restored album “Euro 2004.” Both the album and theimage content have been restored to the iPhoto™ application. In someimplementations, the user can choose to restore only the image content.For example, images can be selected from a backup snapshot and restoredin a new album. Alternatively, the selection can be stored in anexisting album.

The above examples involve backup versions of music libraries or photoalbums. Many different types of applications, items, system settings,preferences, elements or processes can be backed up and made accessiblethrough a time machine. FIG. 15 is a screen shot showing the timemachine interface used with a “Keyboard & Mouse” settings pane. Thisfunction can be one that is provided as part of the operation system 230(FIG. 2). Other aspects of the operating system can similarly be subjectto time machine operations. For example, preferences associated withother input devices, system settings (e.g., display device preferences,printer preferences), and user interface settings (e.g., preferencesdefining a look and feel of the user interface such as colors,background images and, screensaver preferences). [there are probablyother kinds of system settings we can talk about here too]

In this example, a presentation window 1502 is shown displaying a systemsettings interface (e.g., a “control panel”) for keyboard and mousesettings in a computer system. The user can enter the time machineinterface to restore previous system or device settings. Upon enteringthe time machine interface, a timeline 1504 can show snapshotscorresponding to earlier versions of the keyboard and mouse settings.For example, the user may wish to return to a default setting for amouse. Here, the user can search through the timeline 1504 for aprevious setting, such as a default, and select a restore button 1506 torestore the mouse settings to that of the selected snapshot settings. Inaddition, the timeline 1504 can display a “change” indicator 1508 withthe date or filename under the snapshots to indicate a change in aselected snapshot 1510 relative to another snapshot 1512. For example,the snapshot 1512 displays Jul. 13, 2005 and the change indicator 1508because there are differences between the selected snapshot 1510 and theJul. 13, 2005 snapshot 1508.

The user can wish to compare settings between two snapshots withoutinitially restoring either of them. Some implementations can include acompare icon 1514 that a user can select to display both snapshots inthe presentation window for comparison.

As another example, FIG. 16 is a screen shot showing a time machineinterface for an address book application (which can be a distinctapplication or part of another application such as an e-mailapplication). In this example, a presentation window 1602 is showing anaddress book application. Address book information within theapplication can be revised over time, and the time machine applicationcan be used to restore, for example, lost or deleted contact informationwithin an address book. In some implementations, the user can restore adirectory of contacts by selecting a snapshot that includes at least onedirectory not present in a current snapshot.

The user can also restore a complete address book by selecting aparticular snapshot containing the address book and next selecting arestore button 1604. As shown in FIG. 16, the time machine interface, inthis implementation, does not include a timeline for the user to selectsnapshots from. In some implementations the user can navigate throughsnapshots using the control buttons 406 a and 406 b. As another example,the timeline can appear as a rollover effect when a cursor or thepointing device is placed on the corresponding area of the interface. Insome implementations, the user can select an item timeline icon 1606 toopen a timeline view of snapshots, which can present text informationabout one or more snapshots and optionally facilitate navigation to anysnapshot. In some implementations, the timeline view can be toggled offand on using the item timeline icon 1606.

The time machine interface can also be used to present backupinformation relating to an e-mail application. For example, the user canenter the time machine interface to restore any or all contents or dataassociated with the e-mail application, such as data associated with aninbox folder, a sent items folder, a deleted items folder, an addressbook, calendar, preferences, or any other data of the e-mailapplication. For example, in one implementation, the user can restoreinbox messages that were permanently deleted from the e-mailapplication. The user can enter the time machine interface and select asnapshot that includes the deleted inbox messages. In oneimplementation, the user can restore the entire inbox from thatsnapshot. Alternatively, the user can select only particular inboxmessages to restore using the time machine interface. Similarly, theuser can restore deleted message from other folders as well as contactinformation that was deleted.

In another implementation, the time machine interface can be used topresent backup information associated with a messaging application. Forexample, the user can enter the time machine interface to restore one ormore deleted friends from a “buddy list”, deleted conversations,preferences, and the like.

In the above description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding. Itwill be apparent, however, to one skilled in the art thatimplementations can be practiced without these specific details. Inother instances, structures and devices are shown in block diagram formin order to avoid obscuring the disclosure.

In particular, one skilled in the art will recognize that otherarchitectures and graphics environments can be used, and that theexamples can be implemented using graphics tools and products other thanthose described above. In particular, the client/server approach ismerely one example of an architecture for providing the functionalitydescribed herein; one skilled in the art will recognize that other,non-client/server approaches can also be used. Some portions of thedetailed description are presented in terms of algorithms and symbolicrepresentations of operations on data bits within a computer memory.These algorithmic descriptions and representations are the means used bythose skilled in the data processing arts to most effectively convey thesubstance of their work to others skilled in the art. An algorithm ishere, and generally, conceived to be a self-consistent sequence of stepsleading to a desired result. The steps are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the discussion, it isappreciated that throughout the description, discussions utilizing termssuch as “processing” or “computing” or “calculating” or “determining” or“displaying” or the like, refer to the action and processes of acomputer system, or similar electronic computing device, thatmanipulates and transforms data represented as physical (electronic)quantities within the computer system's registers and memories intoother data similarly represented as physical quantities within thecomputer system memories or registers or other such information storage,transmission or display devices.

An apparatus for performing the operations herein can be speciallyconstructed for the required purposes, or it can comprise ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program can bestored in a computer readable storage medium, such as, but is notlimited to, any type of disk including floppy disks, optical disks,CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), randomaccess memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, orany type of media suitable for storing data including electronicinstructions, and each coupled to a computer system bus.

The algorithms and modules presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems can be used with programs in accordance with the teachingsherein, or it can prove convenient to construct more specializedapparatuses to perform the method steps. The required structure for avariety of these systems will appear from the description. In addition,the present examples are not described with reference to any particularprogramming language. It will be appreciated that a variety ofprogramming languages can be used to implement the teachings asdescribed herein. Furthermore, as will be apparent to one of ordinaryskill in the relevant art, the modules, features, attributes,methodologies, and other aspects can be implemented as software,hardware, firmware or any combination of the three. Of course, wherevera component is implemented as software, the component can be implementedas a standalone program, as part of a larger program, as a plurality ofseparate programs, as a statically or dynamically linked library, as akernel loadable module, as a device driver, and/or in every and anyother way known now or in the future to those of skill in the art ofcomputer programming. Additionally, the present description is in no waylimited to implementation in any specific operating system orenvironment.

The subject matter described in this specification can be implemented asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a computer readable medium forexecution by, or to control the operation of, data processing apparatus.The instructions can be organized into modules (or engines) in differentnumbers and combinations from the exemplary modules described. Thecomputer readable medium can be a machine-readable storage device, amachine-readable storage substrate, a memory device, a composition ofmatter effecting a machine-readable propagated signal, or a combinationof one or more them. The term “data processing apparatus” encompassesall apparatus, devices, and machines for processing data, including byway of example a programmable processor, a computer, or multipleprocessors or computers. The apparatus can include, in addition tohardware, code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, or acombination of one or more of them. A propagated signal is anartificially generated signal, e.g., a machine-generated electrical,optical, or electromagnetic signal, that is generated to encodeinformation for transmission to suitable receiver apparatus.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of what may be claimed, but ratheras descriptions of features specific to particular implementations ofthe subject matter. Certain features that are described in thisspecification in the context of separate embodiments can also beimplemented in combination in a single embodiment. Conversely, variousfeatures that are described in the context of a single embodiment canalso be implemented in multiple embodiments separately or in anysuitable subcombination. Moreover, although features may be describedabove as acting in certain combinations and even initially claimed assuch, one or more features from a claimed combination can in some casesbe excised from the combination, and the claimed combination may bedirected to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

The subject matter of this specification has been described in terms ofparticular embodiments, but other embodiments can be implemented and arewithin the scope of the following claims. For example, the actionsrecited in the claims can be performed in a different order and stillachieve desirable results. As one example, the processes depicted in theaccompanying figures do not necessarily require the particular ordershown, or sequential order, to achieve desirable results. In certainimplementations, multitasking and parallel processing may beadvantageous. Other variations are within the scope of the followingclaims.

1. A method comprising: receiving, while a current view of anapplication is displayed in a user interface, a first user inputrequesting that a history view associated with the current view of theapplication be displayed; displaying the history view in response to thefirst user input, the history view including at least a first visualrepresentation of an earlier version of the current view of theapplication, the earlier version including a first element; receiving,while the history view is displayed, a second user input requesting thatthe current view of the application be modified according to the earlierversion, at least with regard to the first element; and modifying, inresponse to the second user input, the current view of the applicationaccording to the earlier version, at least with regard to the firstelement.
 2. The method of claim 1, where the first user input requestingthe history view is initiated in the current view of the application. 3.The method of claim 1, where the second user input requests that themodification be limited to the first element, and wherein themodification modifies the current view of the application to include thefirst element and does not otherwise modify the current view of theapplication.
 4. The method of claim 1, where the first element is aparticular set of application data that is not stored as typical filedata.
 5. The method of claim 4, where the set of application dataincludes mail messages.
 6. The method of claim 4, where the set ofapplication data includes address book entries.
 7. The method of claim4, where the set of application data includes audio data.
 8. The methodof claim 1, where the first visual representation is included in atimeline presented in the history view, the timeline including severalvisual representations of earlier versions of the current view of theapplication.
 9. The method of claim 8, where the earlier versions of thecurrent view of the application were obtained at times defined by aschedule.
 10. The method of claim 8, where the earlier versions of thecurrent view of the application were obtained at times defined by arule.
 11. The method of claim 8, where the earlier versions of thecurrent view of the application were obtained at times when at least onepredefined event occurred.
 12. The method of claim 8, where the historyview further includes an input control for modifying the timeline toinclude only at least one of the visual representations whosecorresponding earlier version differs from the current view of theapplication.
 13. The method of claim 8, where the history view includesa rollover function providing that the timeline is displayed when auser-controlled cursor is located over the timeline, and that thetimeline is not displayed when the user-controlled cursor is not locatedover the timeline.
 14. The method of claim 1, where the application isan audio-application and the first element is a playlist.
 15. The methodof claim 1, where the application is an e-mail application and the firstelement is an inbox.
 16. The method of claim 1, where the application isan e-mail application and the first element is a calendar.
 17. Themethod of claim 1, where the application is an address book applicationand the first element is a directory of contacts.
 18. The method ofclaim 1, where the application is a messaging application and the firstelement is a buddy list.
 19. A computer program product, encoded on acomputer-readable medium, operable to cause data processing apparatus toperform operations comprising: receiving, while a current view of anapplication is displayed in a user interface, a first user inputrequesting that a history view associated with the current view of theapplication be displayed; displaying the history view in response to thefirst user input, the history view including at least a first visualrepresentation of an earlier version of the current view of theapplication, the earlier version including a first element; receiving,while the history view is displayed, a second user input requesting thatthe current view of the application be modified according to the earlierversion, at least with regard to the first element; and modifying, inresponse to the second user input, the current view of the applicationaccording to the earlier version, at least with regard to the firstelement.
 20. A computer program product encoded on a computer-readablemedium, the computer program product including instructions that, whenexecuted, generate on a display device a user interface comprising: aview display area for presenting a current view of an application; ahistory view display area for presenting a history view associated withthe current view of the application, the history view including at leasta first visual representation of an earlier version of the current viewof the application; and an input control for initiating a restoration ofthe current view of the application according to at least a portion ofthe earlier version.
 21. The computer program product of claim 20, wherethe earlier version includes at least a first element that a user canselect, and wherein initiation of the input control after the selectioninitiates the restoration of the current view of the applicationaccording to only the first element of the earlier version.
 22. Thecomputer program product of claim 20, where the first visualrepresentation is included in a timeline presented in the history view,the timeline including several visual representations of earlierversions of the current view of the application.
 23. The computerprogram product of claim 22, where the history view further includesanother input control for modifying the timeline to include only atleast one of the visual representations whose corresponding earlierversion differs from the current view of the application.
 24. A methodcomprising: defining one or more criteria for capturing a state of aview of a user interface of an application; capturing the state of theview in accordance with the criteria; receiving a prompt to suspendpresentation of a current view and present a captured view; andreinstating the captured view into the current view of the userinterface.
 25. The method of claim 24, where defining the one or morecriteria includes receiving a user input in the user interface of theapplication setting one or more parameters associated with the one ormore criteria.
 26. A computer program product, encoded on acomputer-readable medium, operable to cause data processing apparatus toperform operations comprising: defining one or more criteria forcapturing a state of a view of a user interface of an application;capturing the state of the view in accordance with the criteria;receiving a prompt to suspend presentation of a current view and presenta captured view; and reinstating the captured view into the current viewof the user interface.
 27. A method comprising: receiving, while acurrent view of a system settings interface is displayed in a userinterface, a first user input requesting that a history view associatedwith the current view of the system settings interface be displayed;displaying the history view in response to the first user input, thehistory view including at least a first visual representation of anearlier version of the current view of the system setting interface, theearlier version including one or more preferences; receiving, while thehistory view is displayed, a second user input requesting that thecurrent view of the system settings interface be modified according tothe earlier version, at least with regard to a first preference of theone or more preferences; and modifying, in response to the second userinput, the current view of the system settings interface according tothe earlier version, at least with regard to the first preference. 28.The method of claim 27, where the system settings interface is an inputdevice settings interface and the one or more preferences are keyboardand mouse settings.
 29. The method of claim 27, where the systemsettings interface is a user interface settings interface and the one ormore preferences are user interface preferences.